update libEnzyme file name, and add missing strict-aliasing flag #2603
Conversation
|
Thanks for the PR. If you have write access, feel free to merge this PR if it does not need reviews. You can request a review using |
rustbot
added
the
S-waiting-on-review
src/autodiff/debugging.md
Outdated
|
|
||
| ```sh | ||
| <path/to/opt> out.ll -load-pass-plugin=/path/to/llvmenzyme-19.so -passes="enzyme" -s | ||
| <path/to/opt> out.ll -load-pass-plugin=/path/to/build/<target-tripple>/stage1/lib/libEnzyme-21.so -passes="enzyme" -enzyme-strict-aliasing=0 -s |
There was a problem hiding this comment.
tripple -> triple
also LLVMEnzyme-XX is the correct one here, not libEnzyme
There was a problem hiding this comment.
Interestingly enough libEnzyme works! From my local shell:
~/path/to/rust2/build/x86_64-unknown-linux-gnu/llvm/build/bin/opt mod.ll -load-pass-plugin=/path/to/rust2/build/x86_64-unknown-linux-gnu/stage1/lib/libEnzyme-21.so -passes="enzyme" -enzyme-strict-aliasing=0 -o rel3.ll -debug-pass-manager -SWhich is good, because we don't build LLVMEnzyme anymore in our default rust+autodiff setup.
There was a problem hiding this comment.
that's not guaranteed to work and may break if the llvm plugin linking interfaces/libraries change [and may also be system dependent]
probably not wise to put in the docs
There was a problem hiding this comment.
I added a warning. The problem about LLVMEnzyme is that it's not build by default and I think it also requires LLVM's plugin infrastructure, which we don't enable in our LLVMs by default. I'll leave it for now and bring it up on the rust side when we discuss how to distribute Enzyme in CI.
There was a problem hiding this comment.
I'm still really skeptical of putting something into the docs that is not supposed to work (but may only work by accident).
ZuseZ4
force-pushed
the
autodiff-updates
branch
from
815f0cc to
559196a
Compare
rustbot
removed
the
S-waiting-on-review
No description provided.